Skip to content

8353950: Clipboard interaction on Windows is unstable #1911

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

matthiasblaesing
Copy link

@matthiasblaesing matthiasblaesing commented Jun 22, 2025


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • JDK-8353950 needs maintainer approval
  • JDK-8332271 needs maintainer approval

Issues

  • JDK-8353950: Clipboard interaction on Windows is unstable (Bug - P4 - Approved)
  • JDK-8332271: Reading data from the clipboard from multiple threads crashes the JVM (Bug - P3 - Approved)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/1911/head:pull/1911
$ git checkout pull/1911

Update a local copy of the PR:
$ git checkout pull/1911
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/1911/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1911

View PR using the GUI difftool:
$ git pr show -t 1911

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/1911.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Jun 22, 2025

👋 Welcome back mblaesing! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Jun 22, 2025

@matthiasblaesing This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8353950: Clipboard interaction on Windows is unstable
8332271: Reading data from the clipboard from multiple threads crashes the JVM

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 61 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot changed the title Backport 92be7821f5d5cbf5fe0244b41b2b7b1ada898df0 8353950: Clipboard interaction on Windows is unstable Jun 22, 2025
@openjdk
Copy link

openjdk bot commented Jun 22, 2025

This backport pull request has now been updated with issues from the original commit.

@openjdk openjdk bot added backport Port of a pull request already in a different code base clean Identical backport; no merge resolution required labels Jun 22, 2025
@openjdk
Copy link

openjdk bot commented Jun 22, 2025

⚠️ @matthiasblaesing This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.

@openjdk openjdk bot added the rfr Pull request is ready for review label Jun 22, 2025
@mlbridge
Copy link

mlbridge bot commented Jun 22, 2025

Webrevs

@matthiasblaesing
Copy link
Author

Same testing as for master + jdk25 was applied to the backport:

  • Tests from test/jdk/java/awt/Clipboard were successfully run with fastdebug and release configuration. It was verified, that the new test fails before the change and succeeds afterwards.
  • Application level test already done with the original change were repeated and verified

@matthiasblaesing
Copy link
Author

Can I somehow help to get this into an JDK 21 update release?

@jerboaa
Copy link
Contributor

jerboaa commented Jul 9, 2025

This seems ok.

@matthiasblaesing You need to follow instructions for approval to move this forward. See #1911 (comment) and Contributing section in https://wiki.openjdk.org/display/JDKUpdates/JDK+21u

@matthiasblaesing
Copy link
Author

/approval

@openjdk
Copy link

openjdk bot commented Jul 9, 2025

@matthiasblaesing usage: /approval [<id>] (request|cancel) [<text>]

@matthiasblaesing
Copy link
Author

/approval JDK-8353950 request Users indicated, that the flaky keyboard, resulting from NetBeans not being able to install historic clipboard fix because of SecurityManager removal is not acceptable behavior.

@openjdk
Copy link

openjdk bot commented Jul 9, 2025

@matthiasblaesing
JDK-8353950: The approval request has been created successfully.

@matthiasblaesing
Copy link
Author

/approval JDK-8332271 request Crashing the VM with regular AWT calls is not acceptable and needs to be fixed.

@openjdk openjdk bot added the approval Requires approval; will be removed when approval is received label Jul 9, 2025
@openjdk
Copy link

openjdk bot commented Jul 9, 2025

@matthiasblaesing
JDK-8332271: The approval request has been created successfully.

@matthiasblaesing
Copy link
Author

@jerboaa thanks for the reply. I indeed missed that, sorry for the noice.

@jerboaa
Copy link
Contributor

jerboaa commented Jul 9, 2025

/approve yes

@openjdk
Copy link

openjdk bot commented Jul 9, 2025

@jerboaa
8353950: The approval request has been approved.
8332271: The approval request has been approved.

@openjdk openjdk bot added ready Pull request is ready to be integrated and removed approval Requires approval; will be removed when approval is received labels Jul 9, 2025
@matthiasblaesing
Copy link
Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Jul 9, 2025
@openjdk
Copy link

openjdk bot commented Jul 9, 2025

@matthiasblaesing
Your change (at version c2fade9) is now ready to be sponsored by a Committer.

@matthiasblaesing
Copy link
Author

@vieiro @jerboaa would one of you be willing to sponsor this change?

@vieiro
Copy link
Contributor

vieiro commented Jul 9, 2025

I'm not sure this will work (note sure if it's updated yet), but let's

/sponsor

@openjdk
Copy link

openjdk bot commented Jul 9, 2025

@vieiro Only Committers are allowed to sponsor changes.

@jerboaa
Copy link
Contributor

jerboaa commented Jul 10, 2025

/sponsor

@openjdk
Copy link

openjdk bot commented Jul 10, 2025

Going to push as commit dc28239.
Since your change was applied there have been 62 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Jul 10, 2025
@openjdk openjdk bot closed this Jul 10, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Jul 10, 2025
@openjdk
Copy link

openjdk bot commented Jul 10, 2025

@jerboaa @matthiasblaesing Pushed as commit dc28239.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@matthiasblaesing
Copy link
Author

@jerboaa thank you
@vieiro thank you too, I saw the vote thread on jdk-updates-dev and thus assumed, that the magic for your commit enablement had already happened 😄

@vieiro
Copy link
Contributor

vieiro commented Jul 11, 2025

@vieiro thank you too, I saw the vote thread on jdk-updates-dev and thus assumed, that the magic for your commit enablement had already happened 😄

Thank you @matthiasblaesing for backporting this! NetBeans users will be happy to see this on 21 by october.

Yeah, these things go slowly I imagine. I'll have to continue abusing committers for sponsoring meanwhile 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Port of a pull request already in a different code base clean Identical backport; no merge resolution required integrated Pull request has been integrated
Development

Successfully merging this pull request may close these issues.

3 participants